Skip to main content
London Borough of Lambeth

Article 4 direction area

There is a problem

  • permitted-development-rights column is missing values

Modified Direction 1 - CAZ

reference
A4D10A15
name
Modified Direction 1 - CAZ
article-4-direction
A4D10
permitted-development-rights

permitted-development-rights missing

uprns
address-texts
geometry
MULTIPOLYGON (((-0.124251 51.486414,-0.124623 51.486524,-0.125057 51.486676,-0.125338 51.486819,-0.125614 51.486908,-0.125679 51.486871,-0.127222 51.485720,-0.127991 51.485308,-0.128469 51.485086,-0.128152 51.484724,-0.127732 51.484709,-0.127095 51.484613,-0.126575 51.484512,-0.126302 51.484467,-0.126391 51.484412,-0.126484 51.484255,-0.126721 51.484014,-0.126945 51.483740,-0.127103 51.483423,-0.127207 51.483101,-0.127383 51.482374,-0.127480 51.482011,-0.126804 51.482233,-0.126033 51.482527,-0.125535 51.482752,-0.125092 51.482992,-0.124603 51.483317,-0.124257 51.483580,-0.123778 51.484020,-0.123483 51.484356,-0.123376 51.484502,-0.123157 51.484745,-0.122869 51.484986,-0.122656 51.485239,-0.122516 51.485452,-0.122359 51.485715,-0.122221 51.485915,-0.122157 51.485935,-0.122085 51.486056,-0.122112 51.486099,-0.122202 51.486175,-0.122308 51.486214,-0.122410 51.486223,-0.122909 51.486215,-0.123264 51.486247,-0.123426 51.486292,-0.123534 51.486345,-0.123621 51.486375,-0.123767 51.486406,-0.124251 51.486414)))
point
POINT (-0.125334 51.484786)
notes
organisation
entry-date
2024-07-11
start-date
2022-10-28
end-date

How to fix this issue

Your dataset is missing the permitted-development-rights column.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve London Borough of Lambeth’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL